Skip to content

Feat/chat service#89

Merged
NotYuSheng merged 2 commits into
devfrom
feat/chat_service
Jul 1, 2025
Merged

Feat/chat service#89
NotYuSheng merged 2 commits into
devfrom
feat/chat_service

Conversation

@jun-create

@jun-create jun-create commented Jul 1, 2025

Copy link
Copy Markdown
Collaborator

Summary

Fixes # 9

--- rename shared_utils/client.py to shared_utils/openai_client.py

Changes Made

  • refactor changes only

Context / Rationale

NA

Related Docs or References

NA

General Checklist

  • [ v ] I have tested these changes locally
  • [ v ] I have updated relevant documentation or added comments where needed
  • [ v ] I have linked relevant issues and tagged reviewers
  • [ v ] I have followed coding conventions and naming standards

@jun-create jun-create requested a review from NotYuSheng as a code owner July 1, 2025 02:27

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @jun-create, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on refactoring the chat_service module to improve code clarity and organization. It includes a rename of a shared utility module for better specificity and an adjustment to how FastAPI routes are defined within the chat router, ensuring the API endpoints remain consistent while improving the underlying routing structure.

Highlights

  • Module Renaming and Import Update: The shared_utils/client.py module has been logically renamed to shared_utils/openai_client.py to more accurately reflect its purpose. This change is reflected in the import statement within chat_service/routers/chat.py.
  • FastAPI Router Configuration Refactor: The APIRouter in chat_service/routers/chat.py has been refactored. The prefix="/chat" argument was removed from the router's initialization, and the /chat path segment was moved directly into the @router.post decorator for the handle_chat endpoint. This maintains the same effective API endpoint path (/chat) while potentially offering more granular control over routing.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily refactors the import path for the OpenAI client and modifies the API endpoint path for the chat service. The change in the API path from /chat/chat/ to /chat/chat is a functional alteration that should be clarified, as it deviates from the 'refactor changes only' description and introduces a potentially redundant path structure.

Comment thread chat_service/routers/chat.py
@jun-create

Copy link
Copy Markdown
Collaborator Author

@NotYuSheng

For your review

@NotYuSheng NotYuSheng left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, 👍

@NotYuSheng NotYuSheng merged commit 07b23da into dev Jul 1, 2025
3 checks passed
@NotYuSheng NotYuSheng deleted the feat/chat_service branch July 1, 2025 02:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants